|
|
|
|
|
|
|
(text box continued on next page) |
|
|
|
|
|
|
|
|
called powderBaby. However, in the Parent interface code part of the Mommy class, you could do the following (assuming the Parent class was instantiated as theParent): |
|
|
|
| |
|
|
|
|
Public Sub Parent_ChangeDiapers ()
the Parent.ChangeDiapers
powderBaby
End Sub |
|
|
|
| | This way you still use the base behavior of the implemented method and add additional method calls to specialize the operation as well. |
|
|
|
|
|
New Term: A modular variable is a variable that has scope only within the module (class or general code) in which it is declared. This declaration, naturally, occurs in the General Declarations section. |
|
|
|
|
|
|
|
|
As mentioned earlier, the CD-ROM contains the code for this chapter. Feel free to load it in Visual Basic and run it. |
|
|
|
|
|
|
|
|
Gearing Up for Code Implementation |
|
|
|
|
|
|
|
|
Remember, as you move toward this new way of doing projects, the main complaint about the entire object-oriented development process is that it takes too long to move a project from inception to production. That's a fair criticism, given that many companies that first undertake the implementation of object technology generally fail because of lack of preparation, migrating poor development and project management habits to the new paradigm, and lack of experienced personnel. At the same time, those critics of object technology ignore the fact that most projects either end disastrously or achieve hardly any of their initial goals for numerous reasons. Your first OO project will be slowthere's no doubt about that. This is because you're forced to think about the proposed system from the point of view of the user. Also, planning for reuse is time-consuming, and the payback for reuse strategies is at least three years on a wide scale. |
|
|
|
|
|
|
|
|
In traditional environments, the programmer placed himself or herself on the same pedestal as the user (sometimes higher!); the programmer's wants were considered as important as the user's. This often led to compromises in products that left the user dissatisfied. If the programmer was boisterous enough, the user was bullied into accepting the application and a month or two later abandoned its use. Because the programmer was typically not around to see this, he or she was left with the erroneous perception that the project was successful. |
|
|
|
|
|